Automations now also support the 'schedules' type:

- `flexmeasures add automation --type schedules` validates the parameters as
  a schedule trigger message (per the AssetTriggerSchema, as accepted by the
  API trigger endpoint, without the asset id). The schedule 'start' may be
  omitted, in which case each run schedules from the run time (floored to the
  message's resolution, if given) — a fixed start draws a warning.
- The runner dispatches schedules automations to the same job creators as the
  API trigger endpoint (sequential or simultaneous), recording trigger meta
  data (origin automation) on the queued jobs; `flexmeasures add schedule
  --as-job` now records origin CLI.
- Job stats for schedules automations are counted from the scheduling job
  cache (asset-level wrap-up jobs and per-sensor device jobs).
- The UI automations page's Schedules tab is now enabled, with automations
  filtered by type per tab.

Part of #2288

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Rbix8k1JfeUWNXEmHEZVpX

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Rbix8k1JfeUWNXEmHEZVpX

Context:
- Schedule automations do not use a data generator, but the reviewed forecast automation schema required one.

Change:
- Make the foreign key nullable while retaining a database check that forecasts always have a generator.
- Add a forward migration without weakening data-source deletion semantics.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Context:
- Review uncovered untested forecast-only options, invalid durations, and DST start calculation.

Change:
- Add CLI and trigger-preparation regressions while retaining forecast sensor validation.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Context:
- Persistence, inherited flex configuration, descendant statistics, and job counts lacked realistic coverage.

Change:
- Move automation service tests under the fresh-database fixture and add end-to-end schedule regressions.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Context:
- API provenance was not asserted across asset and sensor schedule jobs.

Change:
- Verify API trigger metadata on sequential descendants, wrap-up jobs, and sensor jobs.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Context:
- The asset automation page tests still targeted the former single table.

Change:
- Assert type-specific tables, error rendering, filters, and hidden-tab column adjustment.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Context:
- Minimal asset schedules lost stored defaults, invalid timing could execute, provenance was incomplete, and descendant jobs were miscounted.

Change:
- Validate and floor fixed durations safely, inherit stored flex configuration, preserve provenance, and count the jobs actually dispatched.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Context:
- Schedule automation creation silently accepted forecaster settings that could never affect scheduling.

Change:
- Detect supplied forecast-only options and return a user-facing usage error.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Context:
- DataTables initialized in the hidden schedule tab could render with stale column widths.

Change:
- Add tab accessibility state and adjust initialized table columns when a tab becomes visible.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Context:
- The feature guide linked only to the API root and omitted fixed-start and duration constraints.

Change:
- Document canonical fields, runtime start behavior, timing validation, and generator-free schedule automations.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Context:
- Manual testing exposed raw parser exceptions for malformed automation files.

Change:
- Require a user-facing usage error for invalid YAML in both config and parameter files.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Context:
- PyYAML parser errors escaped automation creation without a useful CLI message.

Change:
- Translate malformed config and parameter files into a normal Click usage error.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Context:
- Manual execution showed minimal automations failing for a one-device asset tree.

Change:
- Exercise both simultaneous and sequential dispatch using realistic flex configuration stored on the child asset.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Context:
- A one-device asset tree collapsed to sensor scheduling without a sensor, and sequential dispatch could not resolve its stored output.

Change:
- Preserve asset-triggered flex models as a list and resolve sequential device sensors from stored consumption or production outputs.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Context:
- Scheduling service docstrings did not distinguish single-job and sequential provenance behavior.

Change:
- Document where trigger metadata is stored and correct the simultaneous return description.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Brings in the timezone and catch-up work from #2396, the sensor links, the sortable listing and the review fixes from #2290.

Resolved by keeping both sides, so an automation carries a timezone and a scheduling cursor as well as its input and output sensors,
and the job statistics still scan the scheduling queue for schedule automations while the forecast path is unchanged.

Two resolutions went further than picking a side.
make_cli_options_optional is gone: add_cli_options_from_schema now takes force_optional, which relaxes the same requirement and also hides the forecast options,
which is what a schedule automation wants anyway, since those options only apply to forecasts.
The asset page test no longer expects a single automations table to be hidden, as the listing is now one table per automation type.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

# Conflicts:
#	flexmeasures/data/services/automations.py

Prepare the scheduling configuration through the same scheduler collection path used before queueing, then derive declared input and output sensors so generator-free schedule automations expose their stored flex dependencies and participate in sensor relationships.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Exercise a minimal schedule that inherits its flex model and context from the asset tree, confirming that price inputs, schedule outputs, and the sensor-to-automation relationship are all reported from stored configuration.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

Create a generator-free schedule with stored price and output sensors and assert that the details endpoint returns both dependency sets instead of reporting empty arrays.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>